feat(studio): collections in the sidebar, list, settings and New collection (RFC-0040 step 3) - #86

RFC-0040 / ADR-0042, step 3 of 4. Stacked on #85, which is stacked on #84.

What changes in Studio

• Sidebar › Content: one item per collection in the registry (GET …/collections: declared, inferred from entries, and posts), with:

  • its plural name in Studio's language (unnamed posts stays "Articles");
  • its icon;
  • its entry count;
  • then Collections.

  The registry refreshes after any write to the site, its entries or its collections (onApiWrite).

• /collections: a list template with name, address, entries and whether the collection is named. New collection opens a dialog: plural and singular name in the site's default language, a key derived from the name (immutable, which the dialog says), an icon from the closed set, and an address. The API checks for overlaps (409 path_conflict).

• /collections/$collection: the Articles list, generalised; ArticlesPage shrank from 214 to 197 lines.

  • Category and tag columns and facets appear only when the taxonomy applies to that collection.
  • For collections other than posts, "New entry", "Search entries" and "No entries yet".
  • The collection's icon and description in the header, plus a Settings button for people with site:settings.

• /collections/$collection/settings: a settings template with these sections:

  • Names: per site locale, plus description and icon.
  • Listing: RSS feed, sitemap, default order.
  • Categories & tags: applied through Taxonomy.collections.
  • Address: shown here, changed in Site settings › Collections, which has the redirect preview.

• Redirects and other screens:

  • /articles redirects to /collections/posts and keeps the facets.
  • The editor stays at /articles/$entryId, since entry ids are unique and about 20 screens deep-link there; its breadcrumb now leads to the entry's collection.
  • The comments queue, the language review options and the taxonomy dialog read the registry instead of posts.

Deviations from the RFC (small)

• The editor URL stays /articles/$entryId and does not become /collections/$collection/$entryId.
• The address is edited in Site settings, not on the collection's settings page; the settings page links there.
• Comments per collection stay in Comment settings.
• The Overview still shows recent articles.

Checks

• design:lint clean; size:check ok, with the baseline ratcheted down because ArticlesPage and SiteShell shrank.
• Bundle budget: initial load 419.9 kB of 420 kB.
  • The 12 collection icons load lazily, so the shell does not carry them. Before that change the load was 421.7 kB.
  • Headroom is now about 100 B. The next shell feature will need to make room.
• Studio tests: 1199/1199, including the new test/collections.test.ts.
• i18n:
  • New lazy namespace collections and 6 core keys.
  • Drafts for 18 languages through the translate skill: AI drafts awaiting review, none marked reviewed.
  • i18n:import checks pass, 27/27.
• design:shots at 1440 and 390 px against a copy of the local test site, with this worktree's CLI and Studio: Collections, New collection dialog, Events, Articles, Events settings. All rendered, with no sideways scroll and no console errors. The same session also checked the API end to end:
  • declaring events returned 200;
  • creating an entry in it returned 201;
  • an entry in the undeclared jobs returned 422 collection_undeclared.

Refs #71

🤖 Generated with Claude Code